Systems and methods for application reuse

ABSTRACT

System and methods are provided. In one embodiment, a system includes a master data archiver configured to store a data related to a turbomachine system and a first data collector service system configured to collect the data from the master data archiver. The system also includes a second data collector service system communicatively coupled to the first data collector service system and configured to pull or to push the data from the first data collector service system and a first data archiver configured to receive at least some of the data from the second data collector service system. The system further includes an asset model database storing a plurality of turbomachine tags, wherein the turbomachine tags are configured to categorize the data and a data access system (DAS) configured to provide data access to the first data archiver, the asset model database, or a combination thereof.

BACKGROUND OF THE INVENTION

The subject matter disclosed herein relates to reuse of systems, andmore specifically, the reuse of software systems.

Certain systems, such as an industrial control system, may provide forcapabilities that enable the control and analysis of the industrialcontrol system. For example, the industrial control system may includecontrollers, field devices, and sensors storing data for subsequentanalysis. Software systems may be used to store and analyze the data. Itwould be beneficial to improve reuse of the software systems.

BRIEF DESCRIPTION OF THE INVENTION

Certain embodiments commensurate in scope with the originally claimedinvention are summarized below. These embodiments are not intended tolimit the scope of the claimed invention, but rather these embodimentsare intended only to provide a brief summary of possible forms of theinvention. Indeed, the invention may encompass a variety of forms thatmay be similar to or different from the embodiments set forth below.

In a first embodiment, a system includes a master data archiverconfigured to store a data related to a turbomachine system and a firstdata collector service system configured to collect the data from themaster data archiver. The system also includes a second data collectorservice system communicatively coupled to the first data collectorservice system and configured to pull or to push the data from the firstdata collector service system and a first data archiver configured toreceive at least some of the data from the second data collector servicesystem. The system further includes an asset model database storing aplurality of turbomachine tags, wherein the turbomachine tags areconfigured to categorize the data and a data access system (DAS)configured to provide data access to the first data archiver, the assetmodel database, or a combination thereof. The system additionallyincludes an application programming interface (API) comprising awrite-once compile anywhere (WOCA) object-oriented language andconfigured to provide a communicative interface to at least one of theDAS, the first data archiver, or the asset model database and an APIwrapper configured to use the API to communicate with a write-once runanywhere (WORA) client application and at least one of the DAS, thefirst data archiver, or the asset model database.

In a second embodiment, a method includes storing a data related to aturbomachine system in a master data archiver and collecting the datafrom the master data archiver using a first data collector servicesystem. The method also includes pushing or pulling the data from thefirst data collector service system to a second data collector servicesystem and storing at least some of the data from the second datacollector service system in a first data archiver. The method furtherincludes storing a plurality of turbomachine tags in an asset modeldatabase, wherein the turbomachine tags are configured to categorize thedata and providing data access to the first data archiver, the assetmodel database, or a combination thereof, by using a data access system(DAS). The method additionally includes communicating with the DAS, thefirst data archiver, the asset model database, or a combination thereofby using an application programming interface (API) comprising awrite-once compile anywhere (WOCA) object-oriented language andproviding an API wrapper configured to use the API to communicate with awrite-once run anywhere (WORA) client application and at least one ofthe DAS, the first data archiver, or the asset model database.

In a third embodiment, a non-transitory tangible computer-readablemedium includes executable code. The code includes instructions forstoring a data related to a turbomachine system in a master dataarchiver and collecting the data from the master data archiver using afirst data collector service system. The code also includes instructionsfor pushing or pulling the data from the first data collector servicesystem to a second data collector service system and storing at leastsome of the data from the second data collector service system in afirst data archiver. The code further includes instructions for storinga plurality of turbomachine tags in an asset model database, wherein theturbomachine tags are configured to categorize the data and providingdata access to the first data archiver, the asset model database, or acombination thereof, by using a data access system (DAS). The codeadditionally includes instructions for communicating with the DAS, thefirst data archiver, the asset model database, or a combination thereofby using an application programming interface (API) comprising awrite-once compile anywhere (WOCA) object-oriented language andproviding an API wrapper configured to use the API to communicate with awrite-once run anywhere (WORA) client application and at least one ofthe DAS, the first data archiver, or the asset model database.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the presentinvention will become better understood when the following detaileddescription is read with reference to the accompanying drawings in whichlike characters represent like parts throughout the drawings, wherein:

FIG. 1 is a bock diagram of an embodiment of an industrial controlsystem suitable for application reuse, including a controller;

FIG. 2 is a block diagram of an embodiment of database system includingthe controller of FIG. 1;

FIG. 3 is a flow chart of an embodiment of a process interfacing aclient application with an application programming interface (API);

FIG. 4 is a screen view of an embodiment of a tag data structure;

FIG. 5 is a flow chart of an embodiment of a process for issuing clientapplication requests;

FIG. 6 is a flow chart of an embodiment of a process for reading datausing an API; and

FIG. 7 is a flow chart of an embodiment of a process for writing datausing an API.

DETAILED DESCRIPTION OF THE INVENTION

One or more specific embodiments of the present invention will bedescribed below. In an effort to provide a concise description of theseembodiments, all features of an actual implementation may not bedescribed in the specification. It should be appreciated that in thedevelopment of any such actual implementation, as in any engineering ordesign project, numerous implementation-specific decisions must be madeto achieve the developers' specific goals, such as compliance withsystem-related and business-related constraints, which may vary from oneimplementation to another. Moreover, it should be appreciated that sucha development effort might be complex and time consuming, but wouldnevertheless be a routine undertaking of design, fabrication, andmanufacture for those of ordinary skill having the benefit of thisdisclosure.

When introducing elements of various embodiments of the presentinvention, the articles “a,” “an,” “the,” and “said” are intended tomean that there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.

Industrial automation systems may include controller systems suitablefor interfacing with a variety of field devices, such as sensors, pumps,valves, and the like. For example, sensors may provide inputs to thecontroller system, and the controller system may then derive certainactions in response to the inputs, such as actuating the valves, drivingthe pumps, and so on. In certain controller systems, such as the Mark™VIe controller system, available from General Electric Co., ofSchenectady, N.Y., data from components of the industrial automationsystem may be stored in a database system for subsequent analysis andprocessing. For example, temperature, pressure, flow rate, clearance(e.g., distance between two components) and vibration data ofturbomachinery (e.g., gas turbine, steam turbine, compressor, pump) maybe used to derive trends, activate alarms, and more generally, toprovide for indications of performance of the turbomachine.

In certain embodiments, the industrial control system may include anapplication programming interface (API) including instructions writtenin a write once compile anywhere (WOCA) object-oriented language, suchas C++. The API may be used to communicatively interface with thedatabase system. For example, the API may include multiple C++ objectsand functions suitable for connecting to the database system,disconnecting from the database system, as well as inserting, updatingand retrieving data from the database system. By using the API, a clientsoftware written in C++ may more efficiently communicate with thedatabase system. However, because the API is coded in a WOCAobject-oriented language, reuse in other object-oriented languages, suchas a write once run anywhere (WORA) objected-oriented language (e.g.,Java), may be difficult. Accordingly, the systems and methods disclosedherein improve reuse of previously written API code by providing for anAPI wrapper suitable for use in the WORA language. In one embodiment,the API wrapper may include some or all of the functionality provided bythe API, and expose the functionality for reuse by client softwarewritten in the WORA language. Additional functionality may also beprovided by the API wrapper, for example, to improve data access to thedatabase system when using the WORA language. By using the API and theAPI wrapper, client software written in multiple languages may moreeasily and efficiently communicate with the database system. Indeed,multiple client software each written in a different language (e.g.,WORA language) may reuse the API.

With the foregoing in mind, it may be useful to describe an embodimentof an industrial control system incorporating techniques disclosedherein, such as a gas turbine system 10 illustrated in FIG. 1. Asdepicted, the turbine system 10 may include a combustor 12. Thecombustor 12 may receive fuel that has been mixed with air, forcombustion in a chamber within combustor 12. This combustion creates hotpressurized exhaust gases. The combustor 12 directs the exhaust gasesthrough a turbine 14 toward an exhaust outlet 16. The turbine 14 may bepart of a rotor. As the exhaust gases pass through the turbine 14, thegases force turbine blades to rotate a drive shaft 18 along an axis ofthe turbine system 10. As illustrated, the drive shaft 18 is connectedto various components of the turbine system 10, including a compressor20.

The drive shaft 18 may include one or more shafts that may be, forexample, concentrically aligned. The drive shaft 18 may include a shaftconnecting the turbine 14 to the compressor 20 to form a rotor. Thecompressor 20 may include blades coupled to the drive shaft 18. Thus,rotation of turbine blades in the turbine 14 causes the shaft connectingthe turbine 14 to the compressor 20 to rotate blades within thecompressor 20. This compresses air in the compressor 20. The rotation ofblades in the compressor 20 compresses air that is received via an airintake 22. The compressed air is fed to the combustor 12 and mixed withfuel to allow for higher efficiency combustion. The shaft 18 may also beconnected to a load 24, which may be a vehicle or a stationary load,such as an electrical generator in a power plant or a propeller on anaircraft. When the load 24 is an electrical generator, the electricalgenerator may be coupled to a power grid 26 for distribution of electricpower to, for example, residential and commercial electricity users.

The turbine system 10 may also include a plurality of sensors and fielddevices configured to monitor a plurality of engine parameters relatedto the operation and performance of the turbine system 10. The sensorsand field devices may include, for example, inlet sensors and fielddevices 30 and outlet sensors and field devices 32 positioned adjacentto, for example, the inlet and outlet portions of the turbine 14 and thecompressor 20, respectively. The inlet sensors and field devices 30 andoutlet sensors and field devices 32 may measure, for example,environmental conditions, such as ambient temperature and ambientpressure, as well as a plurality of engine parameters related to theoperation and performance of the turbine system 10, such as, exhaust gastemperature, rotor speed, engine temperature, engine pressure, gastemperature, engine fuel flow, exhaust flow, vibration, clearancebetween rotating and stationary components, compressor dischargepressure, pollution (e.g., nitrogen oxides, sulfur oxides, carbon oxidesand/or particulate count), and turbine exhaust pressure. Further, thesensors and field devices 30 and 32 may also measure actuatorinformation such as valve position, and a geometry position of variablegeometry components (e.g., air inlet).

The plurality of sensors and field devices 30 and 32 may also beconfigured to monitor engine parameters related to various operationalphases of the turbine system 10. Measurements taken by the plurality ofsensors and field devices 30 and 32 may be transmitted via module lines34 and 36, which may be communicatively coupled to a controller 38. Thecontroller 38 may use the measurements to actively control the turbinesystem 10. Further, the controller 38 and/or the sensors and fielddevices 30 and 32 may store the measurements in a database system, asdescribed in more detail below with respect to FIG. 2. For example,module line 34 may be utilized to transmit measurements from thecompressor 20, while module line 36 may be utilized to transmitmeasurements from the turbine 14. It is to be understood that othersensors may be used, including combustor 12 sensors, exhaust 16 sensors,intake 22 sensors, and load 24 sensors. Likewise, any type of fielddevices may be used, including “smart” field devices such as FieldbusFoundation, Profibus, and/or Hart field devices. It is also to beunderstood that the gas turbine system 10 is only an example embodimentof turbomachinery, and that other gas turbine systems may include, forexample, multiple turbines, multiple shafts, and other arrangement ofsystem 10 components. Alternatively, the turbomachine may not be a gasturbine system 10, but may be a steam turbine, a hydroturbine, or a windturbine.

As mentioned above, the industrial control system 10 may use a databasesystem, such as an embodiment of a database system 40 having a datacollection system 42 and a data analysis system 44, suitable for storingand analyzing turbomachine data, as depicted in FIG. 2. In the depictedembodiment, the data collection system 42 receives data from the turbinesystem 10 such as temperature, pressure, flow rate, vibration, andclearance data, and provides the data to the data analysis system 44 forfurther analysis. In one embodiment, the data is collected throughsensors and field devices 30 and 32, as mentioned above with respect toFIG. 1, by using the controller 38. An open process control (OPC) system46 may then be used to communicatively couple with the controller 38 andtransmit data from the controller 38 into a master data archiver 48. Themaster data archiver 48 may include a database storage system. Forexample, the master data archiver 48 may include a relational database(e.g., Oracle, Microsoft SQL Server, MySQL, PostgreSQL), a networkdatabase (e.g., CODASYL, TurboIMAGE), a file, a noSQL database (e.g.,BaseX, Apache CouchDB, SimpleDB), or any other type of data storage.

The data gathered by the OPC system 46 may include data captured at avariety of time frames or resolutions. For example, the data may becaptured at every millisecond, every 500 milliseconds, every second,every 10 seconds, every hour, and/or every day. Further, the master dataarchiver 48 may store data from any number of turbine systems 10.Indeed, the master data archiver 48 may be communicatively coupled to aplurality of turbine systems 10, and be used as the data repository forthe plurality of turbine systems 10. By aggregating data from one ormore turbine systems 10, the master data archiver 48 may be used toanalyze individual turbine systems 10 as well as a fleet of turbinesystems 10.

A first data collector service 50 included in the data collection system42 may be communicatively coupled to a second data collector service 52included in the data analysis system 44 to distribute data from the datacollection system 42 into the data analysis system 44. In oneembodiment, the data collector service 42 may use a data “push”technique to move data from the data collection system 42 into the dataanalysis system 44. For example, the “push” technique may schedule adata transmission of the master data archiver 48 data into the dataanalysis system 44 at a scheduled time, such as every millisecond, everysecond, every hour, and/or every day. In certain embodiments, the data“push” technique may send the most recently updated data rather than theentire data set found in the master data archiver 48 to more efficientlytransmit the recently updated data. In other embodiments, the datacollector service 52 may use a data “pull” technique to retrieve datafrom the master data archiver 48 into the data analysis system 44. Forexample, the data “pull” technique may schedule the creation of acomputer-executable process at certain times (every millisecond, everysecond, every hour, and/or every day) to retrieve data from the masterdata archiver 48 into the data analysis system 44.

Regardless of the technique used (e.g., “push” and/or “pull”), the datacollector service 52 may then allocate or otherwise partition the dataand store the data in a data archiver 1 referred to by element number54, a data archiver 2 referred to by element number 56, and/or a dataarchiver N referred to by element number 58. The use of multiple dataarchivers 54, 56, 58 enables a more scalable and robust data analysissystem 44. Additional data archivers may be provided as data loadsincrease, and various load balancing database algorithms may be used tomore efficiently distribute queries and/or data updates among the dataarchivers 54, 56, and 58.

In one embodiment, each of the data archivers 54, 56, and 58 may includea proper subset of data stored by the master data archiver 48. That is,the entire master data archiver information may be reconstructed bycombining the data stored in the data archiver 54, 56, and 58. Inanother embodiment, each of the data archivers 54, 56, and 58 mayinclude a full set of the data stored by the master data archiver 48. Anasset model database 60 may also be included and used to categorize thedata found in the data archiver 54, 56, and 58. In one example, thecategorization of the data provided by the asset model database 60 mayinclude the use of a tag data structure. The tag data structure mayencapsulate raw measurement data captured by the sensors and fielddevices 30 and 32, and provide for metadata (e.g., data about data anddata content) suitable for more efficiently retrieving, inserting,updating, and analyzing the measurement data, as described in moredetail below with respect to FIG. 4. A data access system (DAS) 62 mayalso be included in the data analysis system 44. The DAS 62 may providefor efficient data access to the data archivers 54, 56, 58, the assetmodel database 60, or a combination thereof. For example, the DAS 62 mayenable an insert, an update, or a delete of any of the data found in thedata archivers 54, 56, 58, and/or the asset model database 60. The DAS62 may further include a central calculation engine (CCE) 64 and acentral calculation analytical process (CCAP) 66. By using the CCE 64and/or CCAP 66, the DAS 62 may provide for a number of analytics fromthe data received from the master data archiver 48. For example, the DAS62 may provide for trends in the operational performance of the turbinesystem 10.

In one example, temperatures trends, pressures trends, flow rate trends,vibration trends, and/or clearance trends may be provided by the DAS 62(e.g., CCE 64, CCAP 66). A rule trigger workflow 68 may becommunicatively coupled to the DAS 62 to enable certain downstreamprocessing. For example, conditions or trends provided by the DAS 62 maytrigger certain alarms through the rule trigger workflow 68. A serviceoriented architecture (SOA) 70 be communicatively coupled to the ruletrigger workflow 68, and provide for a loosely coupled or tightlycoupled set of software services that enable a set of data accessfunctionality. For example, the SOA 70 may include web-based servicessuitable for informing the user of certain conditions or limits that mayhave been exceeded in the turbine system 10, as well as providing webaccess to the analytics provided by the rule trigger workflow 68.

In the depicted embodiment, an API 72 is also provided. The API 72 maybe coded or written in a WOCA object-oriented language, such as C++,Objective-C, object-oriented COBOL, and the like. The API 72 providesfor objects and functions suitable for interfacing an object-orientedclient application 74 with the DAS 62, the data archivers 54, 56, 58,and the asset data model 60. Indeed, the API 72 may expose all of thefunctionality provided by the DAS 62 to reuse the code and functionalityincluded in the DAS 62. That is, the API 72 may enable theobject-oriented WOCA client application 74 to reuse the objects andfunctions included in the DAS 62. Indeed, the API 72 may be used as aprogrammatic interface to the DAS 62 to provide some or all of thefunctionality provided by the DAS 62, including the analytics providedby the CCE 64 and/or the CCAP 66. By reusing the API 72, a controlengineer or programmer may more efficiently and rapidly create theobject-oriented client application 14.

However, other languages, such as WORA languages (e.g., Java) andprocedural languages such as PERL, Ruby, Python, and Fortran, may not beable to reuse the API 72, because the API 72 may not expose theappropriate programmatic structures suitable for use by languages otherthan the language used to write the API 72. For example, the API 72 maybe included in a dynamic link library (All) and/or a static library file(.lib) stored using a file format incompatible with the file format(s)used by an WORA language client 76. Additionally, data structuresdesigned in a first language (e.g., WOCA language) may be incompatiblewith data structures used in a second language (e.g., WORA language).Further, data types may also be incompatible. For example, an integerdata type may include a big Endian byte ordering (i.e., the mostsignificant byte is the first byte) in the first language, and a littleEndian byte ordering in a second language (i.e., the most significantbyte is the last byte), or vice versa.

The systems and methods described herein provide for a WORA languagewrapper 78 suitable for interfacing with the API 72 with the WORA clientapplication 76. For example, the API wrapper 78 may be included in aJava Native Interface (JNI) .dll and/or .lib file having a file formatcompatible with usage by the WORA client application 76. Indeed, byproviding for the wrapper 78, the systems and methods disclosed hereinenable more efficient reuse of certain components of the database system40, including the data archivers 54, 56, 58, the asset model 60, the DAS62, the rule trigger workflow 68, and the SOA 70.

In one embodiment, a process 80 may be used, as further illustrated inFIG. 3, to interface the client application 76 with the API 72. Theprocess 80 may include code or computer instructions stored in anon-transitory computer readable medium and executable in a computingdevice such as a workstation, laptop, server, tablet, or cell phone. Inthe depicted embodiment, the WORA client application 76 may issue aprogrammatic request (block 82). For example, the WORA clientapplication 76 may desire to connect to the database system 40 shown inFIG. 2, and subsequently request information, insert information, updateinformation, and/or delete information stored in the database system 40.Programmatic requests from the WORA client application 76 that involvethe API 72 may be processed by the API wrapper 78. That is, because theAPI 72 may not be suitable for direct communication with the WORA clientapplication 76, the WORA client application 76 may communicate with theAPI wrapper 78, and the API wrapper 78 may then communicate with the API72. Accordingly, the API wrapper 78 may process the request issued bythe WORA client application 76 and communicate the request to the API 72(block 84). By providing for an interface to the API 72, the API wrapper78 may enable the reuse of a subset or all of the API 72. The API 72 maythen process the request (block 86). For example, the API 72 may read orwrite data stored by the database system 40, including data stored inthe data archivers 54, 56, 58, the asset model database 60, and datamanipulated by the DAS 62, rule trigger workflow 68, and SOA 70.

Some client 76 requests may result in data output. For example, a readrequest may produce one or more operational measurements produced by theturbine system 10. The results of the request, including any errors thatmay have occurred during processing, may then be communicated (block 88)to the API wrapper 78 by the API 72. The API wrapper 78 may then processany results and communicate the results to the WORA client application76 (block 90). For example, data types may be converted from the WOCAdata types (e.g., C++ data types) into the WORA language data type(e.g., Java data types). In one embodiment, type casting may be used toconvert the data types. In this embodiment, an explicit type castcomputer instruction, such as “int result=(int) API_result” may be used.It is to be understood that various data types may be similarly typecasted, including but not limited to int, byte, short, long, float,double, boolean, string, and char. Objects in the WORA language may alsobe translated into other structures usable by the client application 76.In this manner, the client application 76 may receive the results of therequest in a desired format and data type, and perform furtherprocessing. For example, the results may include one or more tags, asdescribed below with respect to FIG. 4, that may be used by the clientapplication 76.

FIG. 4 illustrates an embodiment of a screen view 92 of a data structuretag 94 having a name 96 labeled “TAG1.” As mentioned above, the tag 94enables a more efficient storage and retrieval of turbine system 10measurements (e.g., pressure, speed, vibration, flow rate, clearance) byencapsulating the raw measurements and adding a layer of metadata (e.g.,configuration metadata 98, description metadata 100, engineering unitsmetadata 102, and/or tag type meta data 104 displayed in rows 106 of thescreen view 92), to each raw measurement. A raw measurement may includea number having no other associated data, e.g., the number 3.222. Inother to provide for an ontology or engineering “meaning” to this rawnumber, the tag 94 may add the metadata layers 98, 100, 102, and 104.For example, the engineering units metadata 102 may indicate the type ofengineering unit associated with the raw measurement, such as speed inrevolutions per minute (rpm), temperature (e.g., Fahrenheit, Celsius),pressure (e.g., Pascal, Torr, atmospheric), flow rate (e.g., cubicmeters/second, cubic yards/second), clearance (e.g., millimeters,inches), and/or vibration (e.g., acceleration in millimeters, velocityin inches/seconds). Likewise, the description metadata 100 may be usedto describe the raw measurement associated with the tag 92, such as“shaft speed,” “forward inlet sensor temperature,” “first fuel line flowrate,” “left shroud vibration,”, “aft bearing clearance,” and the like.The tag type metadata 104 may be used to describe the class or type oftag 94 used to encapsulate the raw measurement. Likewise, theconfiguration metadata 98 may be used to denote if the tag 94 has beenprepared for use or is otherwise initialized. By encapsulating a rawmeasurement or measurements in the tag 94, the systems and methodsdescribed herein provide for enhanced database operations, usage andanalysis of raw measurements derived from the sensors and field devices30 and 32 depicted in FIG. 1.

FIG. 5 depicts an embodiment of a process 110. The process 110 mayinclude code or computer instructions executable in a computing devicesuch as a workstation, laptop, server, tablet, or cell phone. In thedepicted process 110, the WORA client application 76 shown in FIG. 2 mayissue (block 112) one or more requests 114, 116, 118, 122, 124, and 126to the API wrapper 78. While the client application 76 may issue any oneor more of the requests 114, 116, 118, 122, 124, and 126 in any order,the client application 76 may generally issue the connect request 114first, followed by one or more of the requests 116, 118, 122, and 124,and then complete the communications with the API wrapper 78 by issuingthe disconnect request 126. In the depicted embodiment, the requests114, 116, 118, 122, 124, and 126 correspond to programmatic functions128, 130, 132, 136, 138, 140. That is, in the depicted embodiment, theclient application 76 issues the requests 114, 116, 118, 122, 124, and126 by programmatically calling the equivalent functions 128, 130, 132,136, 138, 140 included in the API wrapper 78. In one embodiment, thefunctions 128, 130, 132, 136, 138, 140 include computer code orinstructions stored in a dll file (e.g., JNI dll file), Unix sharedobject (so) file, and the like. In another embodiment, the 128, 130,132, 136, 138, 140 include computer code or instructions store in a libfile.

The API wrapper 78 may then programmatically call an equivalentprogrammatic function 142, 144, 146, 150, 152, and 154 included in theAPI 72. In one embodiment, the functions 142, 144, 146, 150, 152, and154 may include computer code or instructions written in anobjected-oriented language (e.g., C++, Eiffel, Objective-C, Smalltalk).The API 72 may then process the function call 142, 144, 146, 150, 152,and/or 154 and interact with the data analysis system 44 (e.g., dataarchivers 54, 56, 58, the asset model database 60, and data manipulatedby the DAS 62, rule trigger workflow 68, and SOA 70) to service therequests 114, 116, 118, 122, 124, and 126. For example, the request 114may result in the API 72 establishing a database connection (block 156).The request 116 may result in the API 72 retrieving a current value(block 158). The request 118 may result in the API 72 retrievingmultiple tag raw data (block 160). The request 122 may result in the API72 retrieving interpolated data (block 164). The request 124 may resultin the API 72 writing data (block 166). The request 126 may result inthe API 72 ending the dataset connection (block 168). The API wrapper 78may then process any results obtained through the API 72 functions 142,144, 146, 150, 152, and 154, and return any results to the clientapplication 76. In this manner, the client application 76 may reuse theAPI 72. In one embodiment, the programmatic functions 114, 116, 118,122, 124, and 126 may be described using C-style or JNI-styleterminology similar to Unix manual pages (e.g., “man” pages), presentedbelow in the following six (6) paragraphs.

Historian_getIHUConnection function 128 establishes a client 76connection to the data analysis system 44. More specifically, thefunction 128 attempts to connect to the data analysis system 44 based oninput parameters and returns a status and a server handle for theresulting connection. PARAMETERS (input): jstring jsusername—The username used to connect. jstring jspassword—The password used to connect.jstring jsservername—The machine or server name of the data analysissystem 44 to connect to. jlong jlmaxRetry—The number of attempts toconnect to the data analysis system 44. jlong jlminSleep—The minimumsleep time (in seconds) used to calculate a wait time for retryattempts. This setting may be initially used to pause/sleep for thefirst retry attempt. For subsequent retry attempts, sleep duration maybe set to previous sleep time+random (0 to minSleep*1000). jlongjlmaxSleep—A maximum sleep time used to set maximum wait time betweenretry attempts. The setting may be used to pause or sleep duringsubsequent retry attempts if the calculated sleep time exceeds thismaximum value. jint jiapiTimeout—An amount of time to attempt toconnect. RETURN (output): jclass connectException—A code exception thatis “thrown” or passed on when a connection status code is not found tobe successful. jlong serverhandle—A unique ID to assign the connection.

Historian_ihuDisconnect function 140—Disconnects the client 76 from thedata analysis system 44. More specifically, the function 140 attempts todisconnect the client 76 from the data analysis system 44 and returns astatus of the disconnection. PARAMETERS (input): jlong serverhandle—Theserver handle denoting a specific data analysis system 44 to disconnect.RETURN (output): jclass connectException—The code exception that is“thrown” or passed on when a disconnection status code is not found tobe successful.

Historian_writeIHUMultiTagData function 138—Writes data to the dataanalysis system 44. More specifically, the function 138 attempts towrite and/or overwrite data into the data analysis system 44 based on aninput array of tags 94. PARAMETERS (input): jlong serverhandle—Theunique connection ID provided by the Historian_getIHUConnection 128.jint numberOfSamples—The number of samples to write. jobjectArrayvalueArray—An array of values used to write into the data analysissystem 44. RETURN (output): jclass ihWriteException—an exception objectthat is “thrown” or passed when the read status code is not successful.

Historian_getIHUMultiTagCurrentValue function 130—Retrieves a range ofdata for multiple tags 94. More specifically, the function 132 attemptsto read the value of multiple tags 94 and returns arrays of sample size,value, timestamp and quality associated with the tags 94 that may havebeen read. PARAMETERS (input): jlong jlserverhandle—The uniqueconnection ID provided by the Historian_getIHUConnection function 128.jobjectArray tagNames—An array of the plurality of tags 94 to be read.jlong jlmaxRetry—The maximum number of times to attempt to read thevalues. Double& retValue—a placeholder for the value of the tag to beread. Long& utc—a placeholder for a timestamp of the returned data set.Long& retQuality—A placeholder for the quality of the returned data set.RETURN (output): jobjectArray multiTagCurValArray—a one-dimensionalarray of DataSample (e.g., Java class data structure) containing anewest raw sample for each tag 94. jclass ihReadException—an exceptionobject that is “thrown” or passed when the read status code is notsuccessful.

Historian_getIHUMultiTagRawDataByTime function 132—Retrieves a range ofdata for multiple tags 94. More specifically, the function 132 attemptsto read the value of multiple tags 94 over a range of time and returnsarrays of sample size, value, timestamp and quality associated with thetags 94. PARAMETERS (input): jlong jlserverhandle—The unique connectionID provided by the Historian_getIHUConnection function 128. jlongtagNames—An array of the plurality of tags 94 to be read. jlongstartTimeinSeconds—The start time in seconds for retrieving values.jlong endTimeInSeconds—The end time in seconds for retrieving values.Jlong maxRetry—The maximum number of times to attempt to read thevalues. RETURN (output): jobjectArray multiTagRawResultArray—a2-dimensional array of DataSample (e.g., java class data structure)containing and array of raw data points for each tag. jclassihReadException—an exception object that is “thrown” or passed when theread status code is not successful.

Historian_getIHUMultiTagInterpData function 136—Retrieves a range ofdata for multiple tags 94 on a specified interval. More specifically,the function 136 attempts to read the value of a plurality of tags 94over an interpolated range of time and then returns various arrays,including arrays of sample size, value, timestamp and quality associatedwith the tags 94. PARAMETERS (input): jlong jlserverhandle—The uniqueconnection ID provided by the Historian_getIHUConnection function 128.jobjectArray tagNames—An array including the name of each of theplurality of tags 94 to be read. jlong jstartTimeInSeconds—The starttime for retrieval of the values. Jlong jlendTimeInSeconds—The end timefor retrieval of the values. jlong jlinterval_sec—An interval (e.g.,seconds) of the data to be read. jint percentGoodTH—The percent goodthreshold used to determine qualitjint percentGoodTH—The percent goodthreshold used to determine quality of the interpolated data point.jlong jImaxRetry—The maximum number of times to attempt to read thevalues. RETURN (output): jobjectArray multiTagRawResultArray—A2-dimensional array of DataSample (e.g., java class data structure)containing the array of interpolated data points for each tag. jclassihReadException—an exception object that is “thrown” or passed when theread status code is not successful.

FIG. 6 is an embodiment of a process 170 that may be used by one of theAPI wrapper 78 functions, such as theHistorian_getIHUMultiTagRawDataByTime function 132 to provide for aninterface between the client application 76 and the API 72 suitable forreading data from the data analysis system 44. The process 170 mayinclude code or computer instructions executable in a computing devicesuch as a workstation, laptop, server, tablet, or cell phone. In thedepicted embodiment, the process 170 may first initialize certainparameters (block 172). For example, internal variables of the function132 may be initialized to desired values before further processing. Inone embodiment, a current retry value (e.g., curRetry) may be comparedto a maximum retry value (e.g., maxRetry) (decision 174). If the currentretry value is greater than the maximum retry value, then the process172 may perform a data cleanup (block 176) and exit the function 132(circle 178). The data cleanup 176 may, for example, initialize anyerror flags with values appropriate for informing of errors, exceptions,and the like. If the current retry value is less than or equal to themaximum retry value (decision 174), then the process 172 may use a “Try”function call to call an API 72 function (block 180), such as the APIfunction ihuReadMultiTagRawDataByTime 146. In the depicted example, the“Try” function call (block 180) has an equivalent “Catch” exceptionhandler (block 182). That is, if there are any processing exceptionsduring the “Try” call to the function 146, the “Catch” exception handler(block 182) may take over processing. For example, the “Catch” exceptionhandler (block 182) may clean up or release memory resources and thenincrement the current retry value (block 184). The process 170 may theniterate back to decision 174.

If the “Try” API call to the function 146 encounters no processingexceptions, then the process 170 may check to determine if the function146 returned successfully and resulted in data (e.g., samples greaterthan zero) (decision 186). If the function 146 returned successfully andresulted in data (e.g., samples greater than zero) (decision 186), thendata structure, such as a sampleArray including a JNI type jobjectArraymay be created (block 188). Other JNI types may be used, such asprimitive types (e.g., boolean, byte, char, short, in, long, float,double, void), reference types, (e.g., jclass, jstring, jarray,jthrowable), field and method IDs (e.g., _jfieldID, _jmethodID), and/orvalue types (e.g., jvalue), as defined by the JNI specification version1.0 and above. Advantageously, the JNI type may be created by using onelanguage (e.g., C, C++) and then mapped into a native data type used ina second language (e.g., Java). For example, an array of characters inC/C++ may be created as a JNI jobjectArray and then mapped into a Javastring. In the presently contemplated embodiment, a customdataSampleClass may be defined in Java. The sampleArray (e.g.,jobjectArray) may then be mapped or translated into a dataSampleClassJava data structure through the use of a JNI function such asSetObjectArrayElement defined in the JNI specification version 1.0 andabove.

Otherwise, if the decision 186 results in a “no,” the process 170 mayincrement the current retry value (block 184) and iterate to decision174. The dataSampleClass may include a native Java data structuressuitable for storing sample data from the turbine system 10. Forexample, the dataSampleClass may include data structures used in storingvalues, times, and quality associated with one or more tags 94.

The process 170 may then query the data type for each sample datareturned by the function 146 (block 190). In certain embodiments, thefunction 146 may provide for a determination of the data types for thedata being read (e.g., int, float, double, short, long, signed,unsigned, and/or char). In one embodiment, the process 170 may data castthe values read by the process (block 192). For example, a C++-style“static_cast<jint>” cast may be used to data cast values into integers.In this same manner, float, double, short, long, signed, unsigned,and/or char data types may be casted. Data casting may more efficientlyand quickly convert the read values into an appropriate data type. Inanother embodiment, the read value may be stored, for example, as astring (e.g., an array of characters) regardless of the originating datatype. In this embodiment, the string may then be converted to a desireddata type, for example, by the WORA client application 76.

The values provided by the API 72 and retrieved via the jobjectArray maythen be converted or otherwise translated into native WORA datastructures (block 194) for subsequent processing by the WORA clientapplication 76. As mentioned above, the JNI environment may provide oneor more functions used to convert or otherwise translate thejobjectArray value, such as the SetObjectArrayElement function and aNewObject function. The process 170 may then perform the data cleanup(block 176), and subsequently exit the function 132 (circle 178). Byproviding an interface between the WORA client 76 and the API 72, theprocess 170 may enable the reuse of functionality included in the API 72in a language (e.g., WORA language) different than originally intended.

FIG. 7 is an embodiment of a process 196 that may be used by one of theAPI wrapper 78 functions, for example, by theHistorian_writeIHUMultiTagData function 138 to provide for an interfacebetween the WORA client application 76 and the API 72 suitable forwriting data into the data analysis system 44. The process 196 mayinclude code or non-tangible computer instructions stored in acomputer-readable medium and executable in a computing device such as aworkstation, laptop, server, tablet, or cell phone. In the depictedembodiment, the process 196 may first initialize certain parameters(block 198). For example, internal variables of the function 138 may beinitialized to desired values before further processing. The process 196may then use a C-style cast to data cast the values to be written (block200). For example, the C-style “(int)” cast may be used to cast valuesinto integers. In this same manner, float, double, short, long, signed,unsigned, and/or char data types may be cast (block 200). One or moredata arrays suitable for use by the API 72 may then be created (block202). For example, the created data arrays may be suitable for use by anobject-oriented language (e.g., C++) used to compile the API 72. Thecast values may then be stored in the data arrays (block 204).

The process 196 may then compare a current retry value (e.g., curRetry)to a maximum retry value (e.g., maxRetry) (decision 206). If the currentretry value is greater than the maximum retry value, then the process196 may perform a data cleanup (block 208) and exit the function 138(circle 210). The data cleanup 208 may, for example, initialize anyerror flags with values appropriate for informing of errors, exceptions,and the like. If the current retry value is less than or equal to themaximum retry value (decision 206), then the process 196 may use a “Try”function call to call (block 212) an API 72 function, such as the APIfunction ihuWriteData 152. In the depicted example, the “Try” functioncall (block 212) has an equivalent “Catch” exception handler (block214). The “Catch” exception handler may take over processing ifprocessing exceptions were to occur during execution of the “Try”function call (block 212). For example, the “Catch” exception handler(block 214) may clean up or release memory resources and then incrementthe current retry value (block 216). The process 196 may then iterateback to decision 206.

If the “Try” API call (block 212) to the API function 152 encounters noexceptions, then the process 196 may check to determine if the write ofthe values was successful (decision 218). If the write operation wassuccessful (decision 218), then the process 196 may perform the datacleanup (block 208) and exit the function 138 (circle 210). Otherwise,the process 196 may increment the current retry value (block 216) anditerate to decision 206. By providing for an interface suitable forwriting data using the API 72, the process 196 may enable the WORAclient application 76 to write data into the data analysis system 40,even though the API 72 may be written using WOCA object-orientedlanguage features.

Technical effects of the invention include enabling the reuse ofexisting systems by providing for a wrapper suitable for interfacingbetween an application programming interface (API) written in a firstWOCA object-oriented language and a client application written in asecond language, such as a WORA object-oriented language. The wrappermay provide for a mapping between data structures in the first languageand data structures in the second language. The wrapper may also providefor data type conversion between data types in the first language anddata types in the second language. A tag data structure may be used toenable a more efficient retrieval of turbomachinery measurement data. Adata collection system and a data analysis system are also described,which may reside in separate computing devices. The data collectionsystem and the data analysis system may be communicatively coupled toeach other, enabling a load balancing of large data sets, and a moreefficient analysis of the turbomachinery data.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal language of the claims.

1. A system comprising: a master data archiver configured to store adata related to a turbomachine system; a first data collector servicesystem configured to collect the data from the master data archiver; asecond data collector service system communicatively coupled to thefirst data collector service system and configured to pull or to pushthe data from the first data collector service system; a first dataarchiver configured to receive at least some of the data from the seconddata collector service system; an asset model database storing aplurality of turbomachine tags, wherein the turbomachine tags areconfigured to categorize the data; a data access system (DAS) configuredto provide data access to the first data archiver, the asset modeldatabase, or a combination thereof; an application programming interface(API) comprising a write-once compile anywhere (WOCA) object-orientedlanguage and configured to provide a communicative interface to at leastone of the DAS, the first data archiver, or the asset model database;and an API wrapper configured to use the API to communicate with awrite-once run anywhere (WORA) client application and at least one ofthe DAS, the first data archiver, or the asset model database.
 2. Thesystem of claim 1, wherein the WORA client application is written in aJava language.
 3. The system of claim 2, wherein the API wrappercomprises a Java Native Interface (JNI) configured to provide atranslation mechanism between the API and the WORA client application.4. The system of claim 1, wherein the WOCA object-oriented languagecomprises at least one of a C++, an Eiffel, an Objective-C, anobject-oriented COBOL or a combination thereof.
 5. The system of claim1, comprising a second data archiver configured to receive at least someof the data from the second data collector service system, wherein theAPI is configured to provide a communicative interface to the seconddata archiver, and the API wrapper is configured to use the API tocommunicate with the second data archiver.
 6. The system of claim 1,wherein the data comprises at least one of a pressure, a flow rate, aspeed, a vibration, a temperature, a clearance, or a combinationthereof.
 7. The system of claim 1, wherein the turbomachine comprises atleast one of a turbine system, a compressor, a pump, or a combinationthereof.
 8. The system of claim 1, comprising a first computing devicehaving the master data archiver and the first data collector servicesystem, and a second computing device having the first data archiver andthe second data collector service system.
 9. The system of claim 1,wherein the first data archiver comprises at least one of a relationaldatabase, a network database, a file, a noSQL database, or a combinationthereof.
 10. The system of claim 1, wherein the API wrapper comprises atleast one of the following: a Historian_getIHUConnection, aHistorian_getIHUMultiTagCurrentValue, aHistorian_getIHUMultiTagRawDataByTime, aHistorian_getIHUMultiTagInterpData, a Historian_writeIHUMultiTagData, aHistorian_IHUDisconnect, or a combination thereof.
 11. A method,comprising: storing a data related to a turbomachine system in a masterdata archiver; collecting the data from the master data archiver using afirst data collector service system; pushing or pulling the data fromthe first data collector service system to a second data collectorservice system; storing at least some of the data from the second datacollector service system in a first data archiver; storing a pluralityof turbomachine tags in an asset model database, wherein theturbomachine tags are configured to categorize the data; providing dataaccess to the first data archiver, the asset model database, or acombination thereof, by using a data access system (DAS); communicatingwith the DAS, the first data archiver, the asset model database, or acombination thereof, by using an application programming interface (API)comprising a write-once compile anywhere (WOCA) object-orientedlanguage; and providing an API wrapper configured to use the API tocommunicate with a write-once run anywhere (WORA) client application andat least one of the DAS, the first data archiver, or the asset modeldatabase.
 12. The method of claim 11, wherein the WORA clientapplication is written in a Java language.
 13. The method of claim 11,wherein the WOCA object-oriented language comprises at least one of aC++, an Eiffel, an Objective-C, an object-oriented COBOL or acombination thereof.
 14. The method of claim 11, wherein the API wrappercomprises at least one of the following: a Historian_getIHUConnection, aHistorian_getIHUMultiTagCurrentValue, aHistorian_getIHUMultiTagRawDataByTime, aHistorian_getIHUMultiTagInterpData, a Historian_writeIHUMultiTagData, aHistorian_IHUDisconnect, or a combination thereof.
 15. A non-transitorytangible computer-readable medium comprising executable code, the codecomprising instructions for: storing a data related to a turbomachinesystem in a master data archiver; collecting the data from the masterdata archiver using a first data collector service system; pushing orpulling the data from the first data collector service system to asecond data collector service system; storing at least some of the datafrom the second data collector service system in a first data archiver;storing a plurality of turbomachine tags in an asset model database,wherein the turbomachine tags are configured to categorize the data;providing data access to the first data archiver, the asset modeldatabase, or a combination thereof, by using a data access system (DAS);communicating with at least one of the DAS, the first data archiver, theasset model database, or a combination thereof, by using an applicationprogramming interface (API) comprising a write-once compile anywhere(WOCA) object-oriented language; and communicating with at least one ofthe DAS, the first data archiver, the asset model database, or acombination thereof, by using an API wrapper configured to use the APIto communicate with a write-once run anywhere (WORA) client applicationand at least one of the DAS, the first data archiver, or the asset modeldatabase.
 16. The non-transitory tangible computer-readable medium ofclaim 15, wherein the WOCA object-oriented language comprises at leastone of a C++, an Eiffel, an Objective-C, an object-oriented COBOL, or acombination thereof.
 17. The non-transitory tangible computer-readablemedium of claim 15, wherein the API wrapper comprises a Java NativeInterface (JNI) configured to provide a translation mechanism betweenthe API and the WORA client application.
 18. The non-transitory tangiblecomputer-readable medium of claim 15, wherein the instructions forcommunicating with the at least one of the DAS, the first data archiver,the asset model database, or a combination thereof, by using the APIwrapper comprise instructions for using at least one of the following: aHistorian_getIHUConnection, a Historian_getIHUMultiTagCurrentValue, aHistorian_getIHUMultiTagRawDataByTime, aHistorian_getIHUMultiTagInterpData, a Historian_writeIHUMultiTagData, aHistorian_IHUDisconnect, or a combination thereof.
 19. Thenon-transitory tangible computer-readable medium of claim 18, whereinthe instructions for using the Historian_getIHUMultiTagRawDataByTimecomprise instructions for: initializing parameters; deciding if acurrent retry count is less than or equal to a maximum retry value;calling an ihuReadMultiTagRawDataByTime included in the API andconfigured to provide sample data based on a name included in theturbomachine tag; and, if the API call is successful and the sample datais greater than zero, then creating a Java Native Interface (JNI)jobjectArray, querying a data type for the sample data, data casting adata cast value based on the data type, storing the data cast value inthe jobjectArray, and performing a data cleanup.
 20. The non-transitorytangible computer-readable medium of claim 18, wherein the instructionsfor using the Historian_writeIHUMultiTagData comprise instructions for:initializing parameters; data casting values; creating an API dataarray; storing casted values in the API data array; deciding if acurrent retry count is less than or equal to a maximum retry value;calling an ihuWriteData included in the API and configured to writesample data based on a name included in the turbomachine tag; and, ifthe API call is successful then performing a data cleanup.